DSTU2
This page is part of the FHIR Specification (v1.0.2: DSTU 2). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions 
SDC System for archiving and retrieving the completed forms
{
"resourceType": "Conformance",
"id": "conformance-sdc-form-archiver",
"text": {
"status": "generated",
"div": "<div>\n \n <h2>SDC Form Archiver</h2>\n \n <p>(Requirements Definition)</p>\n \n <p>Published: 2015-09-03 (draft)</p>\n \n <p>Published by: \n <b>U.S. Office of the National Coordinator (ONC)</b>\n \n </p>\n \n <p>This profile defines the expected capabilities of the \n <i>SDC Form Archiver</i> role when conforming to the S&I Framework's \n <a href=\"sdc.html\">Structured Data Capture FHIR implementation guide</a>. This role is responsible for persisting (archiving) completed or partially completed forms (\n <a href=\"../questionnaireresponse.html\">QuestionnaireResponse</a> resource instances). These instances may be submitted individually or in a bundle together with \n <a href=\"../provenance.html\">Provenance</a> information providing details about the completion of the questionnaire response. In some cases \n <a href=\"../binary.html\">Binary</a> or \n <a href=\"../documentreference.html\">DocumentReference</a> resources might also be submitted to convey source information used in the population of the questionnaire response.<br>The focus of this role is on consuming form instances. Examples might be applications accepting insurance coverage forms, research forms, etc. There is no expectation that submitted form data is subsequently made available for retrieval (at least not in the same format).\n </p>\n \n <h2>General</h2>\n \n <table>\n \n <tbody>\n \n <tr>\n \n <th>FHIR Version:</th>\n \n <td>1.0.2</td>\n \n </tr>\n \n <tr>\n \n <th>Supported formats:</th>\n \n <td>xml, json</td>\n \n </tr>\n \n </tbody>\n \n </table>\n \n <h2>REST behavior</h2>\n \n <p>The \n <a href=\"../questionnaireresponse.html\">QuestionnaireResponse</a> may be sent as a single instance or as a FHIR \n <a href=\"../bundle.html\">Bundle</a> also containing \n <a href=\"../provenance.html\">Provenance</a> resources providing details on the sources of information. A Bundle submission might also include \n <a href=\"../binary.html\">Binary</a> and/or \n <a href=\"../documentreference.html\">DocumentReference</a> instances referring to the data used to populate the form. A Form Archiver must support persisting, searching and retrieving those resources.\n </p>\n \n <p>\n \n <b>Security:</b>\n \n </p>\n \n <p>Implementations must meet the general security requirements documented in the \n <a href=\"sdc-security.html\">SDC implementation guide</a>.\n </p>\n \n <h3>Resource summary</h3>\n \n <table class=\"grid\">\n \n <thead>\n \n <tr>\n \n <th>Resource</th>\n \n <th>Search</th>\n \n <th>Read</th>\n \n <th>Read Version</th>\n \n <th>Instance History</th>\n \n <th>Resource History</th>\n \n <th>Create</th>\n \n <th>Update</th>\n \n <th>Delete</th>\n \n </tr>\n \n </thead>\n \n <tbody>\n \n <tr>\n \n <th>QuestionnaireResponse (\n <a href=\"http://hl7.org/fhir/StructureDefinition/sdc-response\">Profile</a>)\n </th>\n \n <td/>\n \n <td/>\n \n <td/>\n \n <td/>\n \n <td/>\n \n <td>\n \n <a title=\"Allows archiving (storing) a completed or partially-completed form\" href=\"#QuestionnaireResponse-create\">SHALL</a>\n \n </td>\n \n <td>\n \n <a title=\"Allows updating a previously archived form. (Systems may place rules on who can update forms and under what circumstances).\" href=\"#QuestionnaireResponse-update\">SHOULD</a>\n \n </td>\n \n <td>\n \n <a title=\"Allows removal of an archived form from a repository. Note that the removal may be logical rather than physical. Some systems may have rules for who can remove a submitted response and under what circumstances.\" href=\"#QuestionnaireResponse-delete\">MAY</a>\n \n </td>\n \n </tr>\n \n <tr>\n \n <th>Binary</th>\n \n <td/>\n \n <td/>\n \n <td/>\n \n <td/>\n \n <td/>\n \n <td>\n \n <a title=\"Allows storage of a binary (generally containing information used in the completion of a QuestionnaireResponse). The data might be in a variety of forms.\" href=\"#Binary-create\">SHOULD</a>\n \n </td>\n \n <td>\n \n <a title=\"Allows updating a previously submitted binary data. (Systems may place rules on who can update binary data and under what circumstances).\" href=\"#Binary-update\">MAY</a>\n \n </td>\n \n <td>\n \n <a title=\"Allows removal of binary data from a repository. Note that the removal may be logical rather than physical. Some systems may have rules for who can remove binary data and under what circumstances.\" href=\"#Binary-delete\">MAY</a>\n \n </td>\n \n </tr>\n \n <tr>\n \n <th>DocumentReference</th>\n \n <td/>\n \n <td/>\n \n <td/>\n \n <td/>\n \n <td/>\n \n <td>\n \n <a title=\"Allows storage of a document reference (generally containing information used in the completion of a QuestionnaireResponse).\" href=\"#DocumentReference-create\">SHOULD</a>\n \n </td>\n \n <td>\n \n <a title=\"Allows updating a previously submitted document reference. (Systems may place rules on who can update document references and under what circumstances).\" href=\"#DocumentReference-update\">MAY</a>\n \n </td>\n \n <td>\n \n <a title=\"Allows removal of document references from a repository. Note that the removal may be logical rather than physical. Some systems may have rules for who can remove document references and under what circumstances.\" href=\"#DocumentReference-delete\">MAY</a>\n \n </td>\n \n </tr>\n \n <tr>\n \n <th>Provenance</th>\n \n <td/>\n \n <td/>\n \n <td/>\n \n <td/>\n \n <td/>\n \n <td>\n \n <a title=\"Allows submitting a Provenance record associated with a particular QuestionnaireResponse.\" href=\"#Provenance-create\">SHOULD</a>\n \n </td>\n \n <td/>\n \n <td/>\n \n </tr>\n \n </tbody>\n \n </table>\n \n <h3>General interactions</h3>\n \n <table class=\"list\">\n \n <thead>\n \n <tr>\n \n <th>Name</th>\n \n <th>Conformance</th>\n \n <th>Description</th>\n \n </tr>\n \n </thead>\n \n <tbody>\n \n <tr>\n \n <th>\n \n <a name=\"-transaction\"> </a>\n \n <span>transaction</span>\n \n </th>\n \n <td>SHOULD</td>\n \n <td>\n \n <p>Modes: </p>\n \n <p>Allows submission of a \n <a href=\"../questionnaireresponse.html\">QuestionnaireResponse</a> together with \n <a href=\"../provenance.html\">Provenance</a> and other supporting resources as a single unit of work.\n </p>\n \n </td>\n \n </tr>\n \n </tbody>\n \n </table>\n \n <br/>\n \n <br/>\n \n <h3>\n \n <a href=\"../questionnaireresponse.html\">QuestionnaireResponse</a>\n \n </h3>\n \n <h4>Interactions</h4>\n \n <table class=\"list\">\n \n <thead>\n \n <tr>\n \n <th>Name</th>\n \n <th>Conformance</th>\n \n <th>Description</th>\n \n </tr>\n \n </thead>\n \n <tbody>\n \n <tr>\n \n <th>\n \n <a name=\"QuestionnaireResponse-create\"> </a>\n \n <span>create</span>\n \n </th>\n \n <td>SHALL</td>\n \n <td>\n \n <p>Allows archiving (storing) a completed or partially-completed form</p>\n \n </td>\n \n </tr>\n \n <tr>\n \n <th>\n \n <a name=\"QuestionnaireResponse-update\"> </a>\n \n <span>update</span>\n \n </th>\n \n <td>SHOULD</td>\n \n <td>\n \n <p>Allows updating a previously archived form. (Systems may place rules on who can update forms and under what circumstances).</p>\n \n </td>\n \n </tr>\n \n <tr>\n \n <th>\n \n <a name=\"QuestionnaireResponse-delete\"> </a>\n \n <span>delete</span>\n \n </th>\n \n <td>MAY</td>\n \n <td>\n \n <p>Allows removal of an archived form from a repository. Note that the removal may be logical rather than physical. Some systems may have rules for who can remove a submitted response and under what circumstances.</p>\n \n </td>\n \n </tr>\n \n </tbody>\n \n </table>\n \n <br/>\n \n <br/>\n \n <h3>\n \n <a href=\"../binary.html\">Binary</a>\n \n </h3>\n \n <h4>Interactions</h4>\n \n <table class=\"list\">\n \n <thead>\n \n <tr>\n \n <th>Name</th>\n \n <th>Conformance</th>\n \n <th>Description</th>\n \n </tr>\n \n </thead>\n \n <tbody>\n \n <tr>\n \n <th>\n \n <a name=\"Binary-create\"> </a>\n \n <span>create</span>\n \n </th>\n \n <td>SHOULD</td>\n \n <td>\n \n <p>Allows storage of a binary (generally containing information used in the completion of a \n <a href=\"../questionnaireresponse.html\">QuestionnaireResponse</a>). The data might be in a variety of forms.\n </p>\n \n </td>\n \n </tr>\n \n <tr>\n \n <th>\n \n <a name=\"Binary-update\"> </a>\n \n <span>update</span>\n \n </th>\n \n <td>MAY</td>\n \n <td>\n \n <p>Allows updating a previously submitted binary data. (Systems may place rules on who can update binary data and under what circumstances).</p>\n \n </td>\n \n </tr>\n \n <tr>\n \n <th>\n \n <a name=\"Binary-delete\"> </a>\n \n <span>delete</span>\n \n </th>\n \n <td>MAY</td>\n \n <td>\n \n <p>Allows removal of binary data from a repository. Note that the removal may be logical rather than physical. Some systems may have rules for who can remove binary data and under what circumstances.</p>\n \n </td>\n \n </tr>\n \n </tbody>\n \n </table>\n \n <br/>\n \n <br/>\n \n <h3>\n \n <a href=\"../documentreference.html\">DocumentReference</a>\n \n </h3>\n \n <h4>Interactions</h4>\n \n <table class=\"list\">\n \n <thead>\n \n <tr>\n \n <th>Name</th>\n \n <th>Conformance</th>\n \n <th>Description</th>\n \n </tr>\n \n </thead>\n \n <tbody>\n \n <tr>\n \n <th>\n \n <a name=\"DocumentReference-create\"> </a>\n \n <span>create</span>\n \n </th>\n \n <td>SHOULD</td>\n \n <td>\n \n <p>Allows storage of a document reference (generally containing information used in the completion of a \n <a href=\"../questionnaireresponse.html\">QuestionnaireResponse</a>).\n </p>\n \n </td>\n \n </tr>\n \n <tr>\n \n <th>\n \n <a name=\"DocumentReference-update\"> </a>\n \n <span>update</span>\n \n </th>\n \n <td>MAY</td>\n \n <td>\n \n <p>Allows updating a previously submitted document reference. (Systems may place rules on who can update document references and under what circumstances).</p>\n \n </td>\n \n </tr>\n \n <tr>\n \n <th>\n \n <a name=\"DocumentReference-delete\"> </a>\n \n <span>delete</span>\n \n </th>\n \n <td>MAY</td>\n \n <td>\n \n <p>Allows removal of document references from a repository. Note that the removal may be logical rather than physical. Some systems may have rules for who can remove document references and under what circumstances.</p>\n \n </td>\n \n </tr>\n \n </tbody>\n \n </table>\n \n <br/>\n \n <br/>\n \n <h3>\n \n <a href=\"../provenance.html\">Provenance</a>\n \n </h3>\n \n <h4>Interactions</h4>\n \n <table class=\"list\">\n \n <thead>\n \n <tr>\n \n <th>Name</th>\n \n <th>Conformance</th>\n \n <th>Description</th>\n \n </tr>\n \n </thead>\n \n <tbody>\n \n <tr>\n \n <th>\n \n <a name=\"Provenance-create\"> </a>\n \n <span>create</span>\n \n </th>\n \n <td>SHOULD</td>\n \n <td>\n \n <p>Allows submitting a Provenance record associated with a particular \n <a href=\"../questionnaireresponse.html\">QuestionnaireResponse</a>.\n </p>\n \n </td>\n \n </tr>\n \n </tbody>\n \n </table>\n \n </div>"
},
"name": "SDC Form Archiver",
"status": "draft",
"publisher": "U.S. Office of the National Coordinator (ONC)",
"contact": [
{
"telecom": [
{
"system": "other",
"value": "http://wiki.siframework.org/Structured+Data+Capture+Initiative"
}
]
}
],
"date": "2015-09-03",
"description": "This profile defines the expected capabilities of the ''SDC Form Archiver'' role when conforming to the S&I Framework's [[sdc.html|Structured Data Capture FHIR implementation guide]]. This role is responsible for persisting (archiving) completed or partially completed forms ([[QuestionnaireResponse]] resource instances). These instances may be submitted individually or in a bundle together with [[Provenance]] information providing details about the completion of the questionnaire response. In some cases [[Binary]] or [[DocumentReference]] resources might also be submitted to convey source information used in the population of the questionnaire response.<br>The focus of this role is on consuming form instances. Examples might be applications accepting insurance coverage forms, research forms, etc. There is no expectation that submitted form data is subsequently made available for retrieval (at least not in the same format).",
"kind": "requirements",
"fhirVersion": "1.0.2",
"acceptUnknown": "extensions",
"format": [
"xml",
"json"
],
"rest": [
{
"mode": "client",
"documentation": "The [[QuestionnaireResponse]] may be sent as a single instance or as a FHIR [[Bundle]] also containing [[Provenance]] resources providing details on the sources of information. A Bundle submission might also include [[Binary]] and/or [[DocumentReference]] instances referring to the data used to populate the form. A Form Archiver must support persisting, searching and retrieving those resources.",
"security": {
"description": "Implementations must meet the general security requirements documented in the [[sdc-security|SDC implementation guide]]."
},
"resource": [
{
"type": "QuestionnaireResponse",
"profile": {
"reference": "http://hl7.org/fhir/StructureDefinition/sdc-response"
},
"interaction": [
{
"extension": [
{
"url": "http://hl7.org/fhir/StructureDefinition/conformance-expectation",
"valueCode": "SHALL"
}
],
"code": "create",
"documentation": "Allows archiving (storing) a completed or partially-completed form"
},
{
"extension": [
{
"url": "http://hl7.org/fhir/StructureDefinition/conformance-expectation",
"valueCode": "SHOULD"
}
],
"code": "update",
"documentation": "Allows updating a previously archived form. (Systems may place rules on who can update forms and under what circumstances)."
},
{
"extension": [
{
"url": "http://hl7.org/fhir/StructureDefinition/conformance-expectation",
"valueCode": "MAY"
}
],
"code": "delete",
"documentation": "Allows removal of an archived form from a repository. Note that the removal may be logical rather than physical. Some systems may have rules for who can remove a submitted response and under what circumstances."
}
]
},
{
"type": "Binary",
"interaction": [
{
"extension": [
{
"url": "http://hl7.org/fhir/StructureDefinition/conformance-expectation",
"valueCode": "SHOULD"
}
],
"code": "create",
"documentation": "Allows storage of a binary (generally containing information used in the completion of a [[QuestionnaireResponse]]). The data might be in a variety of forms."
},
{
"extension": [
{
"url": "http://hl7.org/fhir/StructureDefinition/conformance-expectation",
"valueCode": "MAY"
}
],
"code": "update",
"documentation": "Allows updating a previously submitted binary data. (Systems may place rules on who can update binary data and under what circumstances)."
},
{
"extension": [
{
"url": "http://hl7.org/fhir/StructureDefinition/conformance-expectation",
"valueCode": "MAY"
}
],
"code": "delete",
"documentation": "Allows removal of binary data from a repository. Note that the removal may be logical rather than physical. Some systems may have rules for who can remove binary data and under what circumstances."
}
]
},
{
"type": "DocumentReference",
"interaction": [
{
"extension": [
{
"url": "http://hl7.org/fhir/StructureDefinition/conformance-expectation",
"valueCode": "SHOULD"
}
],
"code": "create",
"documentation": "Allows storage of a document reference (generally containing information used in the completion of a [[QuestionnaireResponse]])."
},
{
"extension": [
{
"url": "http://hl7.org/fhir/StructureDefinition/conformance-expectation",
"valueCode": "MAY"
}
],
"code": "update",
"documentation": "Allows updating a previously submitted document reference. (Systems may place rules on who can update document references and under what circumstances)."
},
{
"extension": [
{
"url": "http://hl7.org/fhir/StructureDefinition/conformance-expectation",
"valueCode": "MAY"
}
],
"code": "delete",
"documentation": "Allows removal of document references from a repository. Note that the removal may be logical rather than physical. Some systems may have rules for who can remove document references and under what circumstances."
}
]
},
{
"type": "Provenance",
"interaction": [
{
"extension": [
{
"url": "http://hl7.org/fhir/StructureDefinition/conformance-expectation",
"valueCode": "SHOULD"
}
],
"code": "create",
"documentation": "Allows submitting a Provenance record associated with a particular [[QuestionnaireResponse]]."
}
]
}
],
"interaction": [
{
"extension": [
{
"url": "http://hl7.org/fhir/StructureDefinition/conformance-expectation",
"valueCode": "SHOULD"
}
],
"code": "transaction",
"documentation": "Allows submission of a [[QuestionnaireResponse]] together with [[Provenance]] and other supporting resources as a single unit of work."
}
]
}
]
}
Usage note: every effort has been made to ensure that the examples are correct and useful, but they are not a normative part of the specification.
© HL7.org 2011+. FHIR DSTU2 (v1.0.2-7202) generated on Sat, Oct 24, 2015 07:44+1100.
Links: Search |
Version History |
Table of Contents |
Compare to DSTU1 |
|
Propose a change